Motivation

The second bundling step is a pain. It leads to a whole class of new bugs where users are now exposed to both all Vite bugs and all esbuild bugs (or sometimes not bugs, but purposely omitted features such as lack of TypeScript reflection). It also makes it substantially more difficult to understand difficult edge cases because you need to learn two build systems.

Description

Removes esbuild from the adapter-node and netlify adapters. Rich suggested that Vercel and Cloudflare require everything to be in a single file, so I've left the esbuild step for those adapters

Related issues

• Fixes Source maps in adapter-node #2517
• Fixes Type reflection issues #798
• Closes ESBuild define option can break adapter-node assetsMiddleware #2581
• May either fix or at least help with Cannot build with .node files and Vercel adapter #1547
• It might fix this bug though we also have another fix out for it: [Sveltekit v next.175+ with Netlify adapter] Cannot find module 'stream/package.json' #2523 (comment)
• I think there were a couple others I forgot as well

Breaking changes

Adapter authors

• Import app via $server-build alias instead of hard-coded relative path
• Need to specify serverEntryPoint
• Simply import @sveltejs/kit/install-fetch directly instead of more complicated shim

Adapter users

• I removed the options for setting environment variable names in adapter-node. Users can create a custom entry point if they'd like to create environment variables with their own naming scheme
• Users of adapter-node's entryPoint option should switch to the new serverEntryPoint option

Open questions

• Do we like the name $server-build for the alias name?
• Is there some way we can allow typing the app for adapter authors? $server-build doesn't seem to be pulling in types at the moment. I'll leave this for another PR since it's not a regression, but it would be nice to think about